Cellular device security apparatus and method

ABSTRACT

A cellular communication device has one or more access modes which allow reading and writing of data, for example to change its settings, for example passwords and even the entire operating system and also permitting access to personal information such as the user&#39;s telephone book. To prevent cloning and like illegal access activity, the device is configured by restricting access to such data access modes using a device unique security setting. The setting may be a password, preferably a one-time password, or it may be a unique or dynamic or one time configuration of the codes for the read and write instructions of the data mode. There is also disclosed a server, which manages the security settings such that data mode operates during an active connection between the device and the server, and a secure communication protocol for communicating between the server and the cellular device.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/287,098 filed on May 26, 2014, which is a continuation of U.S. patentapplication Ser. No. 14/040,756 filed on Sep. 30, 2013, now U.S. Pat.No. 8,737,963, which is a continuation of U.S. patent application Ser.No. 10/839,148 filed on May 6, 2004, now U.S. Pat. No. 8,548,429, whichclaims the benefit of priority of U.S. Provisional Patent ApplicationNo. 60/550,305 filed on Mar. 8, 2004. The contents of the aboveapplications are all incorporated by reference as if fully set forthherein in their entirety.

FIELD AND BACKGROUND OF THE INVENTION

The present invention relates to cellular device security apparatus andmethods and, more particularly, but not exclusively to a security systemfor protection of data and access thereto, including read and writeaccess to configuration data, in a cellular telephony device.

A security vulnerability exists in cellular devices. In even the mostsecure of current devices it is currently possible to read sensitiveinformation from a cellular device (source) and write it into a newcellular device (destination) thus making the destination deviceidentical to the source device with regards to the cellular network.This enables the destination device to make calls, which are then billedto the source device. Such sensitive information may include deviceinformation such as the network identity of the device. It may alsoinclude personal information such as the user's personal telephone book.

Exploiting the same vulnerability it is also possible to copy sensitiveinformation from a source device to a destination device, thus enablingan end-user device upgrade without the knowledge of the cellularprovider. Likewise it is possible to steal a device in one country andsell it in another country after a new operating system has been writteninto the stolen device.

A cellular device contains the following unique information items thatallow any particular device to be identified uniquely:

1. ESN: Electronic Serial Number. A unique number supplied by themanufacturer of the cellular device.

2. NUM: The cellular device's phone number. supplied by the cellularprovider.

3. A-KEY: Authentication key. Generated, by Synacom Technologies Inc. ofSan Jose, Calif., USA, for each cellular device and cellular providerseparately, supplied by the manufacturer and used for authenticating theidentity of a cellular device by the cellular provider.

4. SSD: An identifier created by the cellular network in combinationwith additional information from the cellular provider's database andused to identify the cellular device when a call is being made.

These four information items are rightly regarded as being extremelysensitive. They are generally located in the cellular device along withthe operating system located on the chipset.

DM (Data Mode)

The DM is a mode in which the device allows any access to the device tochange settings and/or accepts commands, via its serial interface, whichcan be used to read and write information. Setting the device to DMenables reading and writing of data via COM, USB, IR, RF, Bluetooth andany other available interface on the cellular device. There exists adata mode entry command for causing the device to enter data mode, and acode, for example a keypad code, which is required in order to enter DM.The DM code and/or command, is typically unique for each manufacturer.

Cloning a Cellular Device:

Using data mode it is possible to clone a cellular device. The devicesmay be cloned using one of the following three procedures:

-   -   Reading the A-KEY, SSD, ESN and NUM information fields from a        source device and writing them into a destination device.    -   Reading the A-KEY, ESN and NUM information fields from a source        device and writing them into a destination device, and then        requesting a “SSD update” operation from the cellular provider        to receive a valid SSD field.    -   Reading the SSD, ESN and NUM information fields from a source        device and writing them into a destination device.

The A-KEY, SSD, ESN and NUM information fields are all readable from thecellular devices in one way or another.

A single cellular device can be cloned to multiple destination devices,all of which will consequently generate calls billed to the originaldevice.

There are several techniques to read the A-KEY, SSD and the ESNinformation fields and to write them on a new device. One possibilitycomprises using a serial RS-232 or USB cable to connect the sourcecellular device to a personal computer and via a program to read andwrite these fields from the device's operating system.

The cellular devices may be divided into two basic types, deviceswithout protection, in which the information is readable via theoperating system, and devices with password protection. The password isa sixteen (16) hexadecimal digit string (which amounts to eight binaryoctets). Cracking this password is presumably very difficult. When thepassword is known, the ESN, A-KEY, SSD and NUM fields are accessible andcan be read or written. The password is currently manufacturer specific,and therefore if broken once, all devices made by the same manufacturerbecome vulnerable.

The above-described methods for reading and writing information fieldsfrom the devices likewise enable reading and writing the device'soperating system. Some devices have a protection password but it isstill possible to read the operating system without knowing theprotection password, and thus it is possible to obtain the password.

Hacking a Cellular Device:

Cellular devices may be categorized into two general kinds:

1. Devices without passwords: In devices where the data read and datawrite functions are not protected by a password, the operating systemcontains two separate read and write command sets: one set for upgradingthe operating system and one set for reading and writing from theoperating system's memory. These commands can be used directly by ahacker to read the information if the device is the source device, or towrite the information if the device is the destination device.

2. Devices with passwords: A protection password is encoded into thedevice's operating system and thus can be obtained from the binaryoperating system file obtainable on the internet, by theft from thecellular providers or by reading the data from the device.

It is possible to alter the password or to use additional constantlybased, countermeasures to protect the cellular device. The term“constantly based” refers typically to passwords which are different fordifferent manufacturers, different device models, different cellularproviders, different operating systems and versions etc. However asingle password applies to numerous individual devices.

It is noted that the passwords themselves, as well as any additionalcountermeasures, can be decoded from the operating system's binary file,and the binary file has to be distributed to all the cellular providerswho use cellular telephones from the given manufacturer. The passwordsare thus as secure as the weakest provider.

Another method is to obtain the mobile telephone management or PSTprogram which is used to program the cellular devices. PST is a genericterm for programs produced by the manufacturers that are given to thenetwork operators to maintain the cellular device base. The PST programmay then be analyzed, thus obtaining the passwords.

Such an analysis is possible due to the fact that the PST program is astandalone program.

The DIRECTORY field of the mobile telephone, which is a location inwhich sensitive information is stored, is accessible for reading andwriting via the operating system or keypad codes. Therefore a device'sidentification in the data network can be obtained and altered toidentify itself as a different device.

In addition, the operating system can be replaced without a hacker beingrequired to have any knowledge of the protection password. Such areplacement can be used to remove any new safeguards inserted into thenew version of the operating system, thus leaving the device vulnerablewith an old version of the operating system.

The replacement of the operating system can also be used to change thelanguage of the operating system when a cellular device is stolen in onecountry and sold in another country.

As mentioned above, typically, cellular devices have at least two setsof read and write instructions: One set is for upgrading the operatingsystem and one set is for communicating with information fields withinthe operating system.

A further point that is mentioned is that when sending an SMS message,the sender's phone number is a data field which may be filled manuallyby the user and thus a sender can appear to be someone else in the eyesof the receiver.

Cloning software is available from the following exemplary sources:

The UniCDMA cloning program is available from cdmasoftware@ukr.net;

The NVtool cloning program is available from certain forums;

The GTRAN CDMA 1X DATA CARD (800M)_PRL-Ver 3.1 program is available fromcertain forums;

The DM cloning program, by Qualcom, is also available from certainforums.

There is thus a widely recognized need for, and it would be highlyadvantageous to have, a cellular device security system in which accessto the data mode is devoid of the above limitations.

SUMMARY OF THE INVENTION

According to one aspect of the present invention there is provided acellular communication device having an access mode for allowing readingand writing of data to change settings on said cellular communicationdevice, said device being configured with an access restrictor torestrict use of said access mode in accordance with a device uniquesecurity setting.

Preferably, the device unique security setting is comprised physicallyon said device.

Additionally or alternatively, the device unique security setting is asoftware setting.

In an embodiment, said device unique security setting is a codingconfiguration for data read or data write instructions.

Additionally or alternatively, said device unique security setting is adynamic password.

Preferably, the dynamic password is a one-time password.

Preferably, the device unique security setting is constructed using atleast one device specific data item and at least one random data item.

In a particular embodiment of the above, said device unique securitysetting is constructed using two device specific data items and tworandom data items.

Preferably, said device unique security setting is dynamically changedover a series of data access mode operations.

Preferably, said device unique security setting is accessible only via apredetermined communication protocol.

Preferably, said predetermined communication protocol comprises aspecified sequence of communication packets.

Preferably, said predetermined communication protocol comprises aspecified structure of communication packets.

The device may be in physical association with a client program formanaging said predetermined communication protocol.

Preferably, said client program is configured to set said cellularcommunication device into said data access mode for accessing of datawhen it is satisfied that said device unique security setting iscorrect.

According to a second aspect of the present invention there is provideda cellular communication device having a data access mode for allowingreading and writing of data to change settings on said cellularcommunication device, said device being configured to restrict entryinto said data access mode to an active connection involving apredetermined secure server.

Preferably, said active connection is identifiable via a device uniquesecurity setting.

Preferably, said device unique security setting is a codingconfiguration for data read or data write instructions.

Preferably, said device unique security setting is a dynamic password.

In an embodiment, said dynamic password is a one-time password.

In an embodiment, said device unique security setting is constructedusing at least one device specific data item and at least one randomdata item.

Preferably, said device unique security setting is constructed using twodevice specific data items and two random data items.

Preferably, said device unique security setting is dynamically changedover a series of data access mode operations.

Preferably, said device unique security setting is accessible only via apredetermined communication protocol.

Preferably, said predetermined communication protocol comprises aspecified sequence of communication packets.

The device may be provided in association with a client program formanaging said predetermined communication protocol.

Preferably, said client program is configured to set said cellularcommunication device into said data access mode when it is satisfiedthat said device unique security setting is correct.

The client program may be configured to check regularly using saidprotocol that said connection is active, and to disable said data accessmode when said connection is not active.

According to a third aspect of the present invention there is provided aserver for supporting data configuration operations at cellularcommunication devices connecting remotely via a network, the servercomprising a database of unique secure data regarding said cellularcommunication devices and mode access functionality for using saidunique secure data to generate device specific data mode entry commandsrequired at said cellular communication devices, to permit entry intodata mode at said cellular communication devices.

Preferably, the unique secure data seeds a device unique securitysetting.

The device unique security setting may be a coding configuration fordata mode entry, data read or data write instructions.

The device unique security setting may be a dynamic password.

The dynamic password may be a one-time password.

The device unique security setting may be constructed using at least onedevice specific data item and at least one random data item.

Preferably, the device unique security setting is constructed using twodevice specific data items and two random data items.

The device unique security setting may be dynamically changed over aseries of data mode operations.

The device specific data mode entry command may be accessible only via apredetermined communication protocol.

The predetermined communication protocol may comprise a specifiedsequence of communication packets.

The predetermined communication protocol may comprise a specifiedstructure of communication packets.

The server may be located in association with a client program formanaging said predetermined communication protocol.

Preferably, the client program is configured to set said cellularcommunication device into said data mode when it is satisfied that saiddevice specific data mode entry setting is correct.

The client program may be configured to set said cellular communicationdevice to disable said data mode when it appears that a connection withsaid server is not active.

According to a fourth aspect of the present invention there is provideda method of restricting access to a reconfiguration mode of each one ofa plurality of cellular communication devices, the method comprising:

holding device dependent information of each of said plurality ofcellular communication devices,

using said device dependent information to create device unique securitysettings for said plurality of devices, and

configuring said plurality of devices such that a respective deviceunique security setting is required to support said reconfigurationmode.

Preferably, the device dependent information seeds said device uniquesecurity setting.

Preferably, the unique security setting is a coding configuration fordata read or data write instructions of said configuration mode.

The unique security setting may be a dynamic password.

The dynamic password may be a one-time password.

Preferably, said device unique security setting is constructed using atleast one device specific data item and at least one random data item.

Preferably, said device unique security setting is constructed using twodevice specific data items and two random data items.

Preferably, said device unique security setting is dynamically changedover a series of data mode operations.

According to a fifth aspect of the present invention there is provided acellular communication device capable of communication with an externalsource for configuration of said cellular communication device, saidcellular communication device comprising a configuration enabler forenabling or disabling said communication in accordance with a deviceunique security setting.

Preferably, said device unique security setting is comprised physicallyon said device.

Alternatively, said device unique security setting is a softwaresetting.

Unless otherwise defined, all technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art to which this invention belongs. The materials, methods, andexamples provided herein are illustrative only and not intended to belimiting.

Implementation of the method and system of the present inventioninvolves performing or completing certain selected tasks or stepsmanually, automatically, or a combination thereof. Moreover, accordingto actual instrumentation and equipment of preferred embodiments of themethod and system of the present invention, several selected steps couldbe implemented by hardware or by software on any operating system of anyfirmware or a combination thereof. For example, as hardware, selectedsteps of the invention could be implemented as a chip or a circuit. Assoftware, selected steps of the invention could be implemented as aplurality of software instructions being executed by a computer usingany suitable operating system. In any case, selected steps of the methodand system of the invention could be described as being performed by adata processor, such as a computing platform for executing a pluralityof instructions.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is herein described, by way of example only, withreference to the accompanying drawings. With specific reference now tothe drawings in detail, it is stressed that the particulars shown are byway of example and for purposes of illustrative discussion of thepreferred embodiments of the present invention only, and are presentedin the cause of providing what is believed to be the most useful andreadily understood description of the principles and conceptual aspectsof the invention. In this regard, no attempt is made to show structuraldetails of the invention in more detail than is necessary for afundamental understanding of the invention, the description taken withthe drawings making apparent to those skilled in the art how the severalforms of the invention may be embodied in practice.

In the drawings:

FIG. 1 is a simplified diagram showing a cellular telephone having afreely accessible data port for data mode access to anyone who knows thedata mode access code;

FIG. 2 is a simplified diagram showing a first preferred embodiment ofthe present invention, in which a cellular telephone is connectedthrough a data connection to a reprogramming device and to a secureserver;

FIG. 3 is a simplified diagram showing the client server aspects of theembodiment of FIG. 2;

FIG. 4 is a simplified diagram showing another configuration of theclient server aspect of the embodiment of FIG. 2, in which the server isprovided in standalone format;

FIG. 5 is a simplified flow diagram illustrating a procedure forcommunicating between a client and a server for entering and using datamode at a particular cellular device according to a preferred embodimentof the present invention, when the GUI is an integral part of theclient;

FIG. 6 is a simplified flow diagram illustrating a variation of theprocedure of FIG. 5, wherein the GUI is associated with the server;

FIG. 7 is a simplified flow chart illustrating a thread procedure forsecure tracking of a client connection for use with the embodiment ofFIG. 5; and

FIG. 8 is a simplified flow chart showing a thread procedure for securetracking of a client connection for use with the embodiment of FIG. 6.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present embodiments comprise a method and apparatus for protectionof the data mode of the cellular telephony device. Preferably the datamode is protected by a password, and preferably the password is devicespecific. In a further preferred embodiment the password is dynamic andideally is a one-time password. An advantage of a one-time password isthat even if it is picked up by a sniffer program it is already too lateas the cellular device now expects a different password. In analternative embodiment the read and write instructions and/or data modeentry instructions are assigned different codes. Again this ispreferably done in such a way that the codes are different for differentdevices. Again preferably it is done dynamically and preferably there isa one-time configuration for each time the device enters data mode.

Additionally or alternatively data mode protection is provided by onlyallowing access to the data mode operations whilst a live connection isavailable to a predefined secure server or other network accessiblesecurity arrangement.

Additionally or alternatively data mode protection is provided by onlychanging the data mode keypad code and/or instruction so that they areunique for each device.

Additionally or alternatively data mode protection is provided bydisabling the data mode access until such access is required by anauthorized party, at which time the cellular device is signaled toaccept commands. It is possible that such a signal be provided via aphysical interface or via the cellular network or via any other wirelessinterface or via any external electromagnetic influence.

A preferred embodiment combines restricting the data access mode entry,protecting the read and write instructions with a password and changingthe read and write instructions so that all the passwords, instructionsand codes are unique for each device.

Returning to the password embodiment, the password may be constructedfrom one or more of the unique information items stored on each cellulardevice, such as the A-key, together with one or more dynamicallychanging or random or randomly changing data items. In a preferredembodiment two of the cellular device's unique information items areused together with two other random items.

In a further embodiment of the present invention, a server is providedfor each cellular provider or like body, which manages the unique andpreferably dynamic passwords for each of the devices registered withthat cellular provider. The server provides the passwords in real timeas data mode is entered, and thus the cellular device is only able toenter data mode when a connection is present to the given server. Thisis acceptable for legitimate use, since data mode is only needed forinitial setup, later upgrading and other technical services which onlythe cellular provider carries out. Illegitimate use however becomes verydifficult. In particular, even if an illegitimate user manages to crackthe password for a given device, all he gains is a single device. Theoperation is uneconomic, by contrast to the current state of the artwhere a single password gives access to a very large number of devices.

The principles and operation of a cellular telephony device according tothe present invention may be better understood with reference to thedrawings and accompanying description.

Before explaining at least one embodiment of the invention in detail, itis to be understood that the invention is not limited in its applicationto the details of construction and the arrangement of the components setforth in the following description or illustrated in the drawings. Theinvention is capable of other embodiments or of being practiced orcarried out in various ways. Also, it is to be understood that thephraseology and terminology employed herein is for the purpose ofdescription and should not be regarded as limiting.

Reference is now made to FIG. 1, which illustrates a standard mobilecommunication device 10. Device 10 may work with any of the mobiletelephony standards such as GSM, CDMA, TDMA, 1x, CDMA 2000, GPRS and thelike. Each of these standards provides a high level of protection forcommunication over the airwaves to prevent eavesdropping and the like.In addition to communication over the airwaves, the mobile communicationdevice 10 has a data input 12 which allows the cellular device to beconnected to a computer or like client device 14 to be programmed. Thecellular device may need to be programmed to provide it with anoperating system, to tell it what its telephone number is and the like,to make particular services available to the user and to reprogram andupgrade the cellular device during its lifetime.

Unfortunately, cellular device 10 has no way of knowing whether it iscurrently being connected to legitimate reprogramming client device 14,or to an imposter's reprogramming client device 16. As discussed in thebackground, the imposter's reprogramming client may seek to carry outcloning, or may introduce older versions of the operating system, havingknown weaknesses that the imposter may subsequently exploit or carry outa range of other telecommunications crimes. The cellular device 10 infact enters a data mode in order to be reprogrammed and in that datamode all of the above activities are typically possible.

Again, as discussed in the background, password protection of the datamode is known. However, since data mode is needed for initialprogramming of the device, the passwords tend to be set for all of thedevices of a given manufacturer or for certain models or for particularbatches of those models. The passwords are thus shared between thousandsor millions of devices, and have to be distributed amongst all of thecellular providers. Only one weakness at one provider, or one successfulattempt to attack the password directly, means that all the devicessharing the same password are compromised.

Reference is now made to FIG. 2, which shows a cellular communicationdevice 20 connected for upgrading according to an upgradingconfiguration of a first preferred embodiment of the present invention.Device 20 is in data mode for allowing reading and writing of data tochange the settings and generally to allow reprogramming includingreplacing or updating of the operating system, changing of the telephonenumber and the like. The device 20 is configured to restrict use of thedata mode in accordance with a unique security setting belonging to thedevice. Thus the data mode cannot be used unless the device uniquesecurity setting is provided. In this way it is no longer possible toobtain a single password and thereby compromise a large number ofdevices.

Within the device 20 itself, a mode management unit 22, otherwisereferred to herein as an access restrictor or configuration enabler, maybe provided, either as hardware or as software, to manage the deviceunique security setting to ensure that the data mode can onlysuccessfully be entered upon correct use of the device unique securitysetting, and not otherwise.

The device unique security setting may in one embodiment be a physicalsetting. Each communication device may be set with a series of jumpersor like switches, which may be set in a unique manner for each device.In another embodiment the setting may be made in software.

In one embodiment, the device unique security setting is not in fact apassword as such, but rather is an encoding configuration for the datamode read and write instructions, and the data mode entry command. Eachcellular device has different codes for the various read and writeinstructions of data mode of which there may be several. Thus areprogramming client device 24 does not know, unless it is told, whatthe read and write command codes are for the given device and thereforefails to carry out reprogramming. An authorized device however has thenecessary information, as will be explained in greater detail below andthus can reprogram the device.

In another embodiment the setting is a password. The password is uniqueto the individual device. Without the password the data mode cannot beentered and no reprogramming is possible.

In another embodiment the device unique security setting is a dynamicpassword. That is to say it is a password which is changed at regularintervals. Thus even if the password for a given device is obtained,that password only remains valid for a limited amount of time, afterwhich the device ceases to be compromised.

In a preferred embodiment, the dynamic password is a one-time password,that is to say the password is used only once to enter data mode. Onceit has been used it is discarded and a new password is needed for anysubsequent entries into data mode. The principles of dynamic andone-time passwords are also applicable to the command encodings asdescribed above. Thus each device can have dynamically changing commandcodes and even one-time command codes. In a particularly preferredembodiment the commands are in fact changed after every single read orwrite action.

Several methods for providing dynamic and one-time passwords aredescribed below and persons skilled in the field of cryptography willknow of other possibilities.

In one embodiment, the device unique security setting is constructedusing one or more of the device specific data items given above in thebackground and one or more random data items. That is the devicespecific item or items as well as the random item or items may forexample be used to seed either a password generator or command codegenerator. In a preferred embodiment seeding involves a hashingfunction. A hashing function is useful because the one-way property ofthe function enables the mobile device to authenticate the passwordwithout it being possible in a realistic time frame for an eavesdropperto reproduce the password without the seed data.

In a specific implementation, the device unique security setting isconstructed using two device specific data items and two random orchanging data items.

Using the above embodiments, the device unique security setting can bedynamically changed over a series of data mode operations.

In a preferred embodiment of the present invention, the device uniquesecurity settings are dynamic and change rapidly. In such a case it isnot sufficient for reprogramming computer 24 to be able to obtain thesettings. Rather it must have a live connection to a security server 26which knows or generates the settings.

Security server 26 supports data configuration operations at cellularcommunication device 20 which connects remotely via a network, forexample through its data connection 22 and reprogramming computer 24.Alternatively, the device may be connected via a Bluetooth, RFconnection, COM, USB, IR interfaces or any other physical interface.Connection via the cellular network may also be possible, for example byconnecting the server side of the system to the cellular provider'sprovisioning or management networks.

The server preferably comprises a database of unique data of theindividual devices as well as an ability to generate passwords orcommand encodings using that unique data and other random data. Theresulting passwords, instructions etc which it generates constitutedevice specific data mode entry instructions or read and writeinstructions which are required at the cellular communication devices,and permit entry into data mode at the cellular communication devices.

The cellular device has to be secured in such a way as to enable thecellular provider who bought the device to communicate through the datamode of the device to carry out programming and configuration whilepreventing everyone else from communicating with the device through thedata mode.

In the preferred embodiments the data mode is thus protected with apassword or passwords, the passwords being different for each individualcellular device. In alternative embodiments the data communicationcommands are themselves encoded.

In the password embodiment, the password secures communication with thedevice via any interface and for any data mode operation includingdiagnostic and monitoring operations, reading and writing data, andrunning technician programs etc. The device's default mode will be towait for a password before entering data mode. All other operations arepreferably locked until a password is provided and then only theoperations associated with the supplied password are made available.That is to say, in one embodiment it is possible to provide differentpasswords for different access levels. Various levels can be defined sothat different read and write actions require different passwords orsuccessively increasing portions of a larger, more secure password.

The construction of the password or passwords is explained in greaterdetail hereinbelow.

In the command encoding embodiment, cellular devices without passwordsare protected by changing the code numbers for the read, write and dataentry mode instructions. As an alternative, it is possible to modifysuch devices by adding passwords to the operating system so that theyprotect the device with a password or passwords as described above.

Reference is now made to FIG. 3 which shows in greater detail theconfiguration of FIG. 2. Server 26 comprises a database 30 and a serverprogram 32. The mobile device 34 is preferably associated with a clientprogram 36. Both the server and the mobile devices are associated with agiven provider's cellular network 38.

The password or passwords and commands may be saved in a centraldatabase 30 located in a secure network, which is preferably unique toeach cellular provider. Thus, no cellular provider has access to anothercellular provider's database and consequently, to its devices. In theone-time password embodiment the central database may not actually storeany passwords but rather the seed information needed at run time togenerate the password, which is never used again.

A client-server program system preferably enables the cellular providerto manage the devices when they are physically connected to a clientside of the secure system. The devices may be connected as describedabove via a reprogrammer's computer and the data port of the device.Alternatively, as mentioned above, the device may be connected via aBluetooth, RF connection, COM, USB, IR interfaces or any other physicalinterface. Connection via the cellular network 38 may be made availableby connecting the server side of the system to the cellular provider'sprovisioning or management networks.

Server program 32 is preferably provided to supply an interface betweenthe database which contains the information needed to communicate withthe cellular device and the client program 36.

The server program preferably contains the algorithms needed tocommunicate with the cellular device and the client program preferablyacts as a remote interface for the server program and, possibly, theGUI.

In an embodiment the algorithms may be located in client program 36rather than in the server program 32. Client program 36 is preferablypart of a client device which the technician carries with him.

Alternatively, the client program may be held within the mobile device37. In this case the mobile device connects via the cellular or datanetwork 38 and an internal client supports the connection to allowsecure modification of the internal parameters of the telephone.

The server system can, if desired, be constructed in a standalone mode.Such a standalone mode is shown in FIG. 4. Parts that are the same as inFIG. 3 are given the same reference numerals and are not referred toagain except as necessary for understanding the present embodiment. Inthe standalone mode the mobile device is connected directly to thesecure server. Such an arrangement may be appropriate in certaincircumstances such as in the case of a cellular provider in a very smallcountry having just a single service center, or in the case of a smallscale network provider.

Communication between the client and the server may be encrypted, so asto prevent eavesdroppers from reading sensitive information whilst it istraversing the cellular provider's internal network using snifferprograms.

In one preferred embodiment the only data operations available without apassword are changing user information via the cellular device'skeypads, for example changing the phone book entries, reading andsending SMSs, and the like.

Devices are typically provided with a keypad code to set the device intoDM (Data Mode). In the preferred embodiments this code is altered, asdescribed hereinbelow for the passwords.

In the following, the production of individual passwords or commandcodes is explained.

Whether considering password values, read instructions, writeinstructions, DM code or other device commands which are to be changedor added, the values may be constructed as follows:

The construction may use one or more random values, whether numeric,alphabetic, alphanumeric or any other. The random values may be memoryareas in the device's operating system or designated fields.

The construction may use a value generated from the contents of the NUMfield.

The construction may use a value generated from the contents of the ESNfield.

The construction may use a value generated from the contents of theA-KEY field.

The construction may use a value generated from the contents of the SSDfield.

The construction may use a product or a function of the contents of oneor more of the following value fields:

NUM field,

ESN field,

A-KEY field,

SSD field, and

a random value or random values. The random values may be memory areasin the device's operating system or designated fields as before.

The construction may further use a value generated from an algorithmwhich is time-dependent and generates a different code for every second,minute or time interval. Further variation or alternative variation maythen be introduced into the result based upon for example one or more ofthe following:

Time.

Challenge-response from the device's keypad.

NUM field,

ESN field,

A-KEY field,

SSD field,

A random value or random values (The random values may be memory areasin the device's operating system or designated fields), and

A seed value or values.

The above described value is hereinafter designated ALG1.

The value can be changed every time the device is connected to thesystem so that a one-time password, command or code results.

The password is then preferably required in order to make changes in thecellular device's operating system. Such changes include disabling thewrite instructions which enable upgrading the operating system,disabling the read commands which can access the operating systemprogram, removing the password or passwords fields from the operatingsystem's binary files and writing them after the operating system hasbeen written into the device, changing the method in which an operatingsystem upgrade is performed, including changing the commands so thatthey are different for each device, and locking of the commands so thata new operating system may be accepted only after a password has beenprovided. Providing of the password and upgrading of the operatingsystem may be as follows:

The system provides a password.

The device accepts or rejects the password.

If accepted, the device accepts a new operating system.

A new password (or the same old password) is written into the device.

The operating system subsequently rejects any new upgrades until thepassword has been received again.

A second method for a password controlled operating system upgrade is asfollows:

The system waits for a valid password or a command, and a flag is set sothat the operating system accepts a new operating system version. Thenew operating system is now written but with an unset flag.

A new password (or the same old password) may then be written into thedevice, the flag set and the operating system rendered usable.

In a further security measure, it is possible to configure the systemsuch that once the ESN value has been written into the device via thesystem, the operating system prevents any subsequent writing to the ESNinformation field.

The A-KEY value may be set to be only writeable and not readable.

It is possible to change the protection password in devices which have apassword and, if possible, to add a password to those devices which donot have a password. The password is preferably unique for each device.

As a further security measure it is possible to provide separatepasswords for different operations. The separate passwords may beprovided as parts of a longer, more secure, password. Alternatively,they can be completely different passwords.

As mentioned above, in one of the embodiments, it is possible to changethe operating system's read and write instructions for the informationfields into different values for different devices. It is furtherpossible to change the periodic command which prevents the cellulardevice from rebooting when in Data Mode (DM).

An additional security measure involves disabling the key codes whichenable changing the A-KEY and DIRECTORY fields via the device's keypad.As discussed above, the DIRECTORY field typically contains theinformation in the NUM field.

Preferred embodiments of the present invention prevent any communicationwith the device's operating system via any of the device interfaces,whether the Keypad, a USB port, a Com port, an IR port, or any otherinterface unless a live connection is present to a secure server asdescribed above. The live connection is preferably verified via theabove-described single or multiple passwords or via the fact that theconnecting device knows the current codes for the data modeinstructions.

One way of protecting data mode via a one-time password is to lock datacommunication, that is DM or Data Mode, with the device's operatingsystem unless a key is entered into the device. The key is different foreach device, as explained above, and generated in a similar method tothe generation of the passwords and commands explained above, so that itis different for each device and, possibly, time-dependent. The systemprompts the user to enter the device's ESN and then provides the user inreturn with the correct code to enable the device's Data Mode. Thedevice is then connected to the system, and the code is immediatelyaltered, that is to say the mobile telephone is issued with the nextkey. The next key is preferably encrypted and passed to the mobiletelephone electronically as data so that it is not available to theuser.

If the device is not connected to the system within a reasonable timeafter the current key is given out an alert may be written to thecentral database.

A further security measure comprises disabling the caller number inputfield when sending an SMS. The contents of the NUM field may be used forthe caller number value, thus preventing senders of SMS messages fromusing false source numbers.

Preferably, in accordance with the present embodiments, each devicearrives from the manufacturer at the cellular provider locked with adifferent password. For example the A-KEY can be used. The password issent to the cellular provider who bought the device along with the ESN,and A-KEY if that is additional to the password. These are delivered tothe cellular provider separately from the devices. It is also possiblefor the manufacturer to generate a separate password from seed valuesand then in fact send the seed values to the cellular provider whorepeats the calculation process.

If the above security procedures are carried out, then the only twokeypad codes that may be left in the device are:

a keypad code to change the contents of the NUM field, and

a keypad code to change device's mode to DM (Data Mode).

Subsequently, the client-server software system with central database,as described above in respect of FIGS. 2, 3 and 4, manages the data modecommunication with the cellular device so that the cellular provider,and he alone, can perform the following actions:

Upgrading of the cellular device's operating system.

Changing the NUM field.

Changing the A-KEY fields: including initial setting and subsequentmodification as necessary.

Setting the ESN field. This is typically a one-time action.

Reading and writing cellular network information fields.

Reading and writing the phone book

Reading and writing additional user information on a large scale such assaved SMS messages, icons, ring tones etc. Clearly the subscriber wouldwish to use these facilities freely but wholesale copying of the entireaddress book and the like may be operations that one would wish toprotect.

The data mode protection features described herein preferably ensurethat the cellular device only accepts changes or return information whenconnected to the client side of the system of the cellular provider whobought the device. Preferably no information is retrievable and noconfiguration information can be written without a connection to thesystem. No changes are admitted if not received from the cellularprovider's system. Alternatively the changes need not come from thesystem, but can only be accepted whilst the cellular device is connectedto the cellular provider's system. In one embodiment, the securing ofthe device may affect all the device's interfaces except the keypad.

Preferred embodiments enable keeping the ESN, NUM, A-KEY and SSD fieldssecure whilst at the same time enabling them to be changed when neededby simply knowing the correct password. The change may thus be made onlyby those who are allowed to do so, thus preferably technicians of thecellular provider who purchased the device from the manufacturer.

Returning to FIG. 3 and server program 32 preferably includes a databaseengine which contains the information need to generate the password orpasswords and read and write instructions for the each cellular device.The information contained is one or more of the following fields: ESN,NUM, A-KEY, SSD and random values, according to the type of protectionchosen.

The following information may be retained in database 30:

First of all the data base may hold cellular device authenticationinformation, such as ESN, current A-KEY, and a new A-KEY, that is anumber sent during current signaling operations to provide the mobiledevice with a new A-KEY for the next time the system is to communicatewith the cellular device. The same may apply to any other field that canbe changed remotely, namely that a next key can be sent during a currentoperation. The database may also hold a device manufacturer and model, alast communication date with the device, a device operating systemversion, and a password or passwords.

Secondly the database may hold a client identification table. The tablemay typically hold the following information: a client IP address, aclient MAC address, and a client identification string. The database mayalso hold a device manufacturer table. The table may hold themanufacturer name, and a manufacturer number, thus various arbitrarynumbers may be assigned by the system to each manufacturer.

The database may also hold a device model table. The model table mayhold data such as the manufacturer number, as described above, and themodel name.

The database may also store alerts or abnormal operations detected inthe system such as a user requesting a DM enabling code and notsubsequently connecting the device to the system.

It is possible that additional information may be kept, such asoperations carried out on different devices, when they have beenperformed and by whom.

It is possible that if the data mode entry keypad code is to be uniquelyset for each device, the code (or its seed information) may be kept inthe database and the required information may then be provided whenneeded after the requesting party is properly identified. In a preferredembodiment, the code is replaced after the device has been connected tothe system.

If the data mode entry instruction is to be uniquely set for eachdevice, the instruction (or corresponding seed information) may be keptin the database and can be provided when the device has been connectedto the system and identified by the user. In a preferred embodiment, theinstruction may be replaced after the device has been connected to thesystem.

As will be understood from the above, transfer of password informationis used in preferred embodiments between the client and the serverprograms. Such transfer is preferably part of an encrypted communicationstream protocol. The protocol may for example be implemented over aTCP/IP (v4 or v6) transport protocol. The protocol defines data packets,and the data packets in one preferred embodiment conform to thestructure given below in table 1.

TABLE 1 Protocol Packet structure Start End Number Length octet octetType Data 1 2 0 1 Number Total packet length 2 2 2 3 Number Packet type3 Variable 4 X + 3 Binary Data (optional field) of length X

One of the packet types defined in the protocol is the sync packet,whose structure is shown below in table 2. In the sync packet, no datafield is available. A sync packet is sent from the client to the serveror the server to the client periodically, say every 500 ms. If a syncpacket is not received within another period, say 10 seconds, then theside which did not receive the sync packet may disconnect.

TABLE 2 Sync Packet Structure Start End Number Length octet octet TypeData 1 2 0 1 Number 4 2 2 2 3 Number 1

In the protocol, a client, that is the mobile device, makes a requestfor a connection to allow data mode. The structure of the Client connectrequest data packet is that given above in table 1. The data field isstructured as shown below in Table 3.

TABLE 3 Structure of the data field in the client connect requestpacket. Start End Number Length octet octet Type Data 1 2 0 1 Number 582 2 2 3 Number  2 3 6 4 9 Binary MAC address of the client PC 3 16 10 25Binary IP address of the client PC: If IPv4 is used, the first 4 octetswill contain the address, other 12 octets will contain zeroes. 24 32 2657 String Client identification string

Following the connect request is a server connect acknowledge, which issent from the server to the client. The data field is structured asshown in table 4

TABLE 4 Structure of the data field in the server acknowledge packetStart End Number Length octet octet Type Data 1 2 0 1 Number 134 2 2 2 3Number  3 3 2 4 5 Number 1: Authenticated. 2: Rejected 4 128 6 133String Error or login message, null terminated

In the continuation of the protocol the server may make a data request.In such a request the data field preferably contains information to bewritten to the interface of the cellular device. The data field isstructured as shown in Table 5.

TABLE 5 server data request - structure of the data field Start EndNumber Length octet octet Type Data 1 2 0 1 Number Total packet length 22 2 3 Number 4 3 Packet 3 Packet Binary Binary data to be writtenlength-4 length - 4 to the interface to which the cellular device isconnected

In response to the server data request is a client data reply. The datafield is structured as shown in table 6 and may contain information readfrom the cellular device.

TABLE 6 Client data reply, structure of the data field Start End NumberLength octet octet Type Data 1 2 0 1 Number Total packet length 2 2 2 3Number 5 3 Packet 4 Packet Binary Binary data read from the length-4length - 4 interface to which the device is connected

In the protocol, the client is able to request a service, such as agiven operation in data mode. A Client service request packet has a datafield structured as shown in table 7 below.

TABLE 7 Client Service request - structure of the data field Start EndNumber Length octet octet Type Data 1 2 0 1 Number 10 2 2 2 3 Number  62 4 4 7 Binary Connected device ESN 3 2 8 9 Number Service request: 1.Device initialization. 2. OS upgrade. 3. A-KEY change. 4. NUM change. 5.Read phone book. 6. Write phone book.

The protocol allows the client device to provide identificationinformation about itself to identify itself to the server. The datafield may be structured as shown in Table 8.

TABLE 8 Client identification information packet - structure of the datafield Start End Number Length octet octet Type Data 1 2 0 1 Number 6 2 22 3 Number 7 3 2 4 5 Number Number which identifies connected cellulardevice manufacturer and model.

The protocol preferably allows client user authentication. The datafield contains the structure shown in table 9.

TABLE 9 Client user authentication - structure of data field Start EndNumber Length octet octet Type Data 1 2 0 1 Number 72 2 2 2 3 Number  83 32 4 35 String User name, null terminated. 4 32 36 67 String Password,null terminated 5 4 68 71 Binary Client IP address

Having considered the communication protocol, a client program is usedat the mobile device to operate the protocol and obtain the informationneeded to run data mode at the device.

The Client program is generally not located within the mobile device butmay be located on another device which connects, physically orotherwise, to the cellular device via a COM, USB or IR interface. Forexample the client may be located on a computer used by the cellularprovider for reprogramming cellular telephones. In another embodimentthe technician actually downloads the client program to the cellulardevice and it connects via a regular wireless connection to the server.This latter embodiment is particularly suitable for cellular enabledpalmtop type devices.

The client program initially connects to the server program whenexecuted, preferably via the protocol defined above.

During the course of the connection, Sync packets are sent periodicallyto and from the server program so that both the server and client knowthat the connection is still live.

The client program reads and writes data to the cellular device via theselected interface following server request signals and provides returndata to the server when data becomes available from the interface.

The graphical user interface (GUI) at the client program preferablyprompts the user for a user name and password. After the user has typedthe information, a data packet is sent to the server and the clientwaits for authentication. Until a data packet is received with an“Authenticated” flag, no operations are allowed at the cellulartelephone.

There are two possibilities for providing the GUI. One is to provide itas part of the client (Graphic User Interface), the other is to provideit as part of the server so that the client accesses it when connectedto the server.

Typical functions of the GUI include selecting an interface forconnecting to the mobile device. Thus, such a function may beimplemented by opening a dialog box which allows the user to select theconnected interface from a list box: say Com1, Com2, Com3, Com4, USB.

A function to select a device type may comprise opening a dialog boxwhich allows the user to select the cellular device type. Thus, two listboxes may be provided, one list box may contain the manufacturer namesand the right list box may contain the relevant models for the selectedmanufacturer, as held by the specific cellular provider.

Before connecting the cellular device to the client, the cellular devicehas to be changed into DM (Data Mode). In order to permit such a changein mode, communication is required with the server as described above.Thus the client program may send a data packet to the server, using theprotocol described hereinabove. In an alternative embodiment thecellular device is first connected to the system and then a data modeentry instruction is sent to the cellular device.

The “Select device type” may then be disabled until an interface hasbeen selected. When the data mode is entered then all or any of theoperations listed below may be selected through the GUI. The operationsmay typically include:

-   -   Initializing a new device.    -   Upgrading the existing device operating system.    -   Updating the A-KEY.    -   Setting the device NUM.    -   Reading a phone book from a connected device.    -   Writing a saved phone book to a connected device. The writing a        phonebook option clearly is only relevant when there is a        phonebook to write and thus the option may be disabled until a        phone book has been read.

The operations menu is preferably disabled, that is prevented from beingselected, until an interface and a device manufacturer and model havebeen selected.

After selecting one of the above operations, a data packet is preferablysent to the server indicating the service selected. In one embodiment ordepending on the operation, the server has to permit the operation. Inother cases the server merely notes that the operation has taken place.

The GUI element of the client may in one embodiment reside in theserver, as an application which provides remote GUI (such as ASP,ASP.NET, PHP, JavaScript). In such a case the following may apply:

The GUI application may communicate with the server program via a TCP/IPsocket or named pipes.

The client program may be a socket server while the server programinitiates the communication.

Except for the above two points, operation is the same whether the GUIis located at the client or at the server.

After the device type has been selected, the client preferably sendsdata packets when data is received via the selected interface,regardless of what operation, if any, it is running. It is optional forthe server to identify the cellular device.

Moving now to the server, and the server program connects to thedatabase and reads and writes information from the database and theclient programs.

Reference is now made to FIG. 5, which shows the procedure when the GUIis an integral part of the client program. As shown in FIG. 5, theserver program waits for connections from client programs, and when aconnection is received it creates a new listening socket, stage 50,waits for a new connection, stage 52, creates a new worker thread forthe incoming connection, stage 54 and returns to stage 50. A thread isan authentication system for data packets to ensure that data packetsare exchanged in the correct order and only whilst the connection issuitably authenticated.

Reference is now made to FIG. 6, which shows what happens when the GUIis not an integral part of the client program. In FIG. 6 the servercreates a new named pipe listener, stage 60, waits for a new connection,62, creates a new worker thread for the incoming connection, 64 andreturns to stage 60.

Reference is now made to FIGS. 7 and 8 which detail the threadprocedures for the two GUI cases. FIG. 7 is a flow chart illustratingthe thread procedure for the case in which the GUI is an integral partof the client program. In this case the server program waits forconnections from client programs. The server waits for a data packet #2.Then if the client IP address and MAC are authenticated it sends a datapacket #3 with “Authenticated” flag. Alternatively, if the IP addressand MAC are not authenticated then it sends packet #3 with a “Rejected”flag and the thread ends.

Subsequently the server waits for data packet #8. If the user name andpassword are authenticated, the thread continues, otherwise it exits.

The server then waits for subsequent requests from the client program,and terminates the thread on socket disconnect.

FIG. 8 illustrates the thread procedure for the case in which the GUI isnot an integral part of the client program.

The server first receives the client IP address, user name and passwordfrom a packet #2. It then waits for a data packet #8 from theconsequently named pipe. If the user name and password areauthenticated, the thread continues, otherwise it exits. An attempt ismade to connect to the client IP. If the connection succeeds the threadcontinues, otherwise it exits. The server then waits for data packet #2.If the client IP address and MAC are authenticated then it sends packet#3 with an “Authenticated” flag. If not, then it sends packet #3 with a“Rejected” flag and the thread ends.

The server then waits for a disconnect of the named pipe or the socket,or socket packets or commands from the named pipes. It then terminatesthe thread on the socket or makes a named pipe disconnect. As long as itis still connected, client requests are processed, allowing for datamode operations on the mobile communication device. After handling therequest, processing returns to receiving the next packet.

During the existence of a connection two types of periodic messages aresent, regardless of the rest of the processing. Sync messages, made upof the sync packets described above in table 2, are preferably sent atregular intervals from the server program to the client program and viceversa.

Furthermore, when a cellular device is connected to the client program,a data packet is sent at regular intervals to prevent the cellulardevice from exiting DM (Data Mode) and/or resetting.

Reference was made above to the services which may be supported usingthe data mode of the cellular telephony device and which may beprotected using the present embodiments. It is noted that each servicerequest is preferably received at the server with the connected device'sESN. A short summary of each of the services listed above is nowprovided.

Device Initialization:

Device initialization according to the preferred embodiments compriseswriting a new ESN to the database, reading the A-KEY from the database,generating a new password for the device from a function of one or moreof the NUM, ESN, A-KEY fields and random values, writing the password tothe database, and setting the password in the device. Setting thepassword comprises sending the appropriate commands in data packetswhich, when written into the interface to which the cellular device isconnected, are able to affect a password change. The server then waitsfor the appropriate response from the cellular device as received fromthe client program, makes additional necessary changes to the deviceand, if needed, replaces the operating system.

OS Upgrade:

Upgrading the operating system according to the presently preferredembodiments comprises retrieving a device password, and replacing theoperating system on the connected device. Replacing the operating systemcomprises sending the appropriate commands in data packets which, whenwritten into the interface to which the cellular device is connected,affect an operating system change. The system then waits for theappropriate response from the cellular device as received from theclient program.

A-KEY Change:

Changing the A-Key, or writing the A-KEY on the connected device usingthe present embodiments comprises sending the appropriate commands indata packets which, when written into the interface to which thecellular device is connected, affect a change in the A-KEY field. Theserver then waits for the appropriate response from the cellular deviceas received from the client program.

NUM Change:

Changing the NUM key or writing the NUM into the cellular devicepreferably comprises sending appropriate commands in data packets which,when written into the interface to which the cellular device isconnected, affect a change in the NUM field. The server then waits forthe appropriate response from the cellular device as received from theclient program.

Read Phone Book:

Reading the phone book of a cellular device according to the presentembodiments preferably comprises sending the appropriate commands indata packets which, when written into the interface to which thecellular device is connected, return the information stored in thedevice's phone book in it's own, proprietary format. The server thenwaits for the appropriate response from the cellular device as receivedfrom the client program. If the phone book information is in a validformat, it may then be converted into a more general format, for examplethat shown in table 10 below.

Write Phone Book:

This service is only applicable if a phone book has been read and needsto be written somewhere. If the phone book can be converted to theconnected device's proprietary format then it is so converted. Then thephone book is written into the next device by sending the appropriatecommands in data packets which, when written into the interface to whichthe cellular device is connected, affect a phone book change.

TABLE 10 Phonebook format Field name Field type Can be empty? Phonenumber String No Name String No Cell number Number No Default cell dialBoolean No Additional information String Yes

It is expected that during the life of this patent many relevantcellular communication devices, cellular networks, network protocols andsystems will be developed and the scope of the terms herein,particularly of the term “cellular device”, is intended to include allsuch new technologies a priori.

It is appreciated that certain features of the invention, which are, forclarity, described in the context of separate embodiments, may also beprovided in combination in a single embodiment. Conversely, variousfeatures of the invention, which are, for brevity, described in thecontext of a single embodiment, may also be provided separately or inany suitable subcombination.

Although the invention has been described in conjunction with specificembodiments thereof, it is evident that many alternatives, modificationsand variations will be apparent to those skilled in the art.Accordingly, it is intended to embrace all such alternatives,modifications and variations that fall within the spirit and broad scopeof the appended claims. All publications, patents and patentapplications mentioned in this specification are herein incorporated intheir entirety by reference into the specification, to the same extentas if each individual publication, patent or patent application wasspecifically and individually indicated to be incorporated herein byreference. In addition, citation or identification of any reference inthis application shall not be construed as an admission that suchreference is available as prior art to the present invention.

What is claimed is:
 1. A cellular communication device having a datamode allowing reading and writing of data and changing of settings onsaid cellular communication device, said settings comprising personaldata, device configuration data and technical data relating to thespecific device, said device being configured with an access restrictorto restrict use of said access data mode in accordance with a deviceunique security setting, wherein said device unique security setting isobtained remotely and provided to the cellular communication device asthe access data mode is entered, said data mode being usable over acellular network.
 2. The cellular device of claim 1, wherein said datamode admits changes that come from a respective cellular provider anddoes not admit changes which do not come from said respective cellularprovider.
 3. The cellular device of claim 1, wherein said data modeadmits changes when connected to a respective cellular provider.
 4. Thecellular device of claim 1, wherein said data mode is usable for readingand writing of cellular network information fields.
 5. A cellularcommunication device having a data mode allowing reading and writing ofdata and changing of settings on said cellular communication device,said settings comprising personal data, device configuration data andtechnical data relating to the specific device, said device beingconfigured with an access restrictor to restrict use of said access datamode in accordance with a device unique security setting, wherein saiddevice unique security setting is obtained remotely and provided to thecellular communication device as the access data mode is entered, saiddata mode being usable to restrict actions comprising uploading,maintaining or replacing an operating system to be carried out only by acellular provider.
 6. The cellular communication device of claim 1,wherein said device unique security setting is one member of the groupconsisting of being a software setting, being a coding configuration fordata read or data write instructions, being a dynamic password, andbeing a one-time password which is changed after each instruction. 7.The cellular communication device of claim 1, wherein said device uniquesecurity setting is constructed using one member of the group consistingof: one device specific data item and one random data item, and twodevice specific data items and two random data items.
 8. The cellularcommunication device of claim 1, wherein said device unique securitysetting is dynamically changed over a series of data access modeoperations.
 9. The cellular communication device of claim 1, whereinsaid device unique security setting is accessible only via apredetermined communication protocol.
 10. The cellular communicationdevice of claim 5, wherein said predetermined communication protocolcomprises one member of the group consisting of: a specified sequence ofcommunication packets, and a specified structure of communicationpackets.
 11. The cellular communication device of claim 5, being inphysical association with a client program for managing saidpredetermined communication protocol.
 12. The cellular communicationdevice of claim 7, wherein said client program is configured to set saidcellular communication device into said data access mode for accessingof data when it is satisfied that said device unique security setting iscorrect.
 13. The cellular communication device of claim 1, wherein saiddevice is configured to restrict entry into said data mode to an activeconnection involving a predetermined secure server (26).
 14. Thecellular communication device according to claim 9, wherein said activeconnection is identifiable via a device unique security setting.
 15. Thecellular communication device of claim 10, wherein said device uniquesecurity setting is one member of the group consisting of a codingconfiguration for data read or data write instructions, a dynamicpassword, and a dynamic password being a one-time password.
 16. Thecellular communication device of claim 9, wherein said device uniquesecurity setting is constructed using one member of the group consistingof: at least one device specific data item and at least one random dataitem, and two device specific data items and two random data items. 17.The cellular communication device of claim 12, wherein said deviceunique security setting is dynamically changed over a series of dataaccess mode operations.
 18. The cellular communication device of claim13, wherein said device unique security setting is accessible only via apredetermined communication protocol.
 19. The cellular communicationdevice of claim 14, wherein said predetermined communication protocolcomprises one member of the group consisting of: a specified sequence ofcommunication packets, and a specified structure of communicationpackets.
 20. The cellular communication device of claim 14, being inassociation with a client program for managing said predeterminedcommunication protocol.
 21. The cellular communication device of claim16, wherein said client program is configured for one member of thegroup consisting of: setting said cellular communication device intosaid data mode when it is satisfied that said device unique securitysetting is correct; and checking regularly using said protocol that saidconnection is active, and to disable said data mode when said connectionis not active.
 22. The cellular communication device of claim 1, furthercomprising a configuration enabler for enabling or disablingcommunication for configuration of said device in accordance with adevice unique security setting.
 23. The cellular device of claim 4,wherein said data mode admits changes that come from a respectivecellular provider and does not admit changes which do not come from saidrespective cellular provider.
 24. The cellular device of claim 4,wherein said data mode admits changes when connected to a respectivecellular provider.